Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 208-tree-1
name: 1182
tree-preservation-order: undefined
208-tpo-1
uprn
address-text
point: POINT (-1.028519 50.866666)
geometry: MULTIPOLYGON (((-1.028491 50.866663,-1.028492 50.866669,-1.028496 50.866674,-1.028510 50.866681,-1.028519 50.866682,-1.028528 50.866681,-1.028536 50.866678,-1.028542 50.866674,-1.028548 50.866664,-1.028547 50.866658,-1.028543 50.866653,-1.028537 50.866649,-1.028520 50.866646,-1.028511 50.866646,-1.028503 50.866649,-1.028497 50.866653,-1.028491 50.866663)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL